fix: jest setup was voiding custom turbo mocks #636
+34
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR updates the
jest.setup.ts
file to make it suitable to be used by projects using the rn google mobile ads library. The docs are updated accordingly.I made sure we only mock our own native modules in the
jest.setup.ts
file so the mocks won't interfere with other libraries' or custom mocks.Related issues
TurboModuleRegistry.get
, breaking test suites #631Checklist
and followed the process outlined there for submitting PRs.
Android
iOS
e2e
tests added or updated in__tests__e2e__
jest
tests added or updated in__tests__
Test Plan
jest.setup.ts
file viasetupFiles
in one of my projects (before I used custom mocks for this library)yarn tests:jest
still passes all tests just like before after I removed thePlatform
mock